fix(cloud): preserve full PR patch fidelity - #131
Merged
Conversation
vincentkoc
marked this pull request as ready for review
July 29, 2026 10:09
osolmaz
pushed a commit
to osolmaz/gitcrawl
that referenced
this pull request
Jul 29, 2026
* fix(cloud): preserve PR patch text in snapshots * docs(cloud): define full-fidelity snapshot boundary * fix(cloud): restore full bodies from portable seeds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Fixes an issue where the Cloudflare SQLite snapshot could inherit clipped portable-store bodies and dropped pull-request patch text even though the hosted archive is intended to retain richer canonical data than the compact Git-backed store.
Why This Change Was Made
Preserve structured PR patch text, truthfully declare source code in bundle privacy metadata, and refresh portable body-length/excerpt metadata whenever a copied portable database is hydrated into a full runtime store. Raw API payloads, blob references, run diagnostics, local code indexes, and machine-local paths remain scrubbed.
User Impact
Cloud archive consumers can recover full canonical issue and pull-request bodies, comments, and PR patch text. Gzip remains lossless transport rather than portable-store compaction.
Evidence
go test ./...git diff --check